-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Squash test to test parent bank after squash #2961
Conversation
599a127
to
9330682
Compare
this isn't covered by the tests in accounts? |
ah, different Accounts impl ;) |
@rob-solana not that i know of, but I admit I didn't look at your recent PR too closely yet to see if that does it. |
Codecov Report
@@ Coverage Diff @@
## master #2961 +/- ##
========================================
- Coverage 78.3% 78.3% -0.1%
========================================
Files 127 127
Lines 19705 19697 -8
========================================
- Hits 15447 15435 -12
- Misses 4258 4262 +4 |
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #2961 +/- ##
========================================
- Coverage 78.3% 78.3% -0.1%
========================================
Files 127 127
Lines 19705 19697 -8
========================================
- Hits 15447 15435 -12
- Misses 4258 4262 +4 |
@rob-solana no I don't see any test that tests that the parent bank is ok after squash. |
my test of accountsdb_squash verifies that the previous db is ok after squash() |
but more tests mo-better ;) |
Problem
Missing test for when a parent's account set is still valid after a child squash.
Summary of Changes
Add a test for this scenario. Impetus is that the persistant accounts PR does not pass this test yet and that causes problems when the bank the RPC module is looking at doesn't match the one that is the latest which has been squashed.
Fixes #